-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix accessor using unsuitable property #964
Conversation
Accessor shouldn't use buffer::property. It looks like there is no real need for `properties` to contain any property, as the test just checks all possible constructors.
b79457f
to
92579dd
Compare
For some reason the runner is reaching the time limit. |
It seems like CI attempts to build all the CTS tests, which takes a while. Not sure why, because |
@bader hi, how should we proceed here? |
Pass CI + get approval from non-Intel implementer => merge PR. Are you asking something else? |
Yes:) The patch can't pass CI. Looks like it builds the whole project and reaches the timelimit. |
I see at least two options to investigate:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
@bader can we treat the current pre-commit status as passed? Looks like the build was successful, the workflow just failed the "Post Set up ccache" step (I guess due to time limit?). Can we merge this? |
I hope #982 will fix problems with |
Accessor shouldn't use buffer::property.
It looks like there is no real need for
properties
to contain any property, as the test just checks all possible constructors.